IRIX Base Documentation 2001 May

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / a_man / cat1 / roboinst.z / roboinst

Wrap

Text File | 2001-04-17 | 26.1 KB | 463 lines

rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) NNNNAAAAMMMMEEEE roboinst, roboinst_start, roboinst_check - automatic software installation tool SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS rrrroooobbbbooooiiiinnnnsssstttt [ ----LLLLnnnnyyyyxxxx ] [ ----bbbb bootdir ] [ ----cccc configdir ] [ ----PPPP disk ] [ ----tttt time ] [ ----gggg grace ] [ ----ffff distribution ] [ ----ssss shell ] [ ----NNNN netinfomode ] [ ----FFFF selectionsfile ] [ ----mmmm mailbox ] host ... rrrroooobbbbooooiiiinnnnsssstttt [ ----rrrrllll ] host ... rrrroooobbbbooooiiiinnnnsssstttt [ ----qqqq ] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _r_o_b_o_i_n_s_t is a tool to help automate the process of upgrading software on a number of hosts. _r_o_b_o_i_n_s_t can help in automating installing and upgrading operating system and application software, installing patches, repartitioning disks, and other software installation tasks. More complete documentation is provided in the online book _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g. This book can be obtained by installing the eoe.books.sgi_admin subsystem using _i_n_s_t(1M) or _S_o_f_t_w_a_r_e _M_a_n_a_g_e_r(1M). Once a boot server, configuration server, and other options have been configured, the superuser executes the _r_o_b_o_i_n_s_t command to actually begin the automatic installation tasks specified in a file called mmmmrrrrccccoooonnnnffffiiiigggg residing in the configuration directory (see -c below). _r_o_b_o_i_n_s_t verifies and starts the automatic installation process on the specified host(s). If no host is given on the command line, the current host is assumed. Unless the -L option is specified, each host is restarted in the miniroot. While in the miniroot, the disks may be repartitioned and software may be installed. Once the installation has completed, the host is restarted in normal user mode. _r_o_b_o_i_n_s_t will log into each host using rrrrsssshhhh((((1111CCCC)))) in order to initiate remote installation requests. This requires an open root account or suitable .rhosts entry on the remote side. The -s option may be used to specify an alternate remote shell program. _r_o_b_o_i_n_s_t verifies and starts the automatic installation process on the specified host(s). If no host is specified on the command line, the current host is assumed. Unless the -L option is specified, each host is restarted in the miniroot. While in the miniroot, the disks may be repartitioned and software may be installed. Once the installation has completed, the host is restarted in normal user mode. Verification is performed by first checking to make sure that boot server and other boot-time information is available, using _b_o_o_t_p(1M). The existence of the ssssaaaa bootfile in the specified bbbboooooooottttddddiiiirrrr is verified, and the configuration server is checked to make sure that the configuration files can be copied. The loghost is determined from the configuration files and a checkpoint file is created in the ////vvvvaaaarrrr////iiiinnnnsssstttt directory. PPPPaaaaggggeeee 1111 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) If the client is not up and running in multi-user mode, or is not accepting remote logins, a roboinst job can be initiated directly from the client's PROM command monitor. See PROM below. OOOOPPPPTTTTIIIIOOOONNNNSSSS The _r_o_b_o_i_n_s_t command accepts the following options: ----bbbb _s_e_r_v_e_r:/_b_o_o_t_d_i_r Specifies the network boot directory on the boot server. A boot server delivers the files necessary for an SGI machine to boot into the miniroot across the network. The boot directory must contain the bootfile ssssaaaa, and also a subdirectory called mmmmiiiinnnniiiirrrrooooooootttt that contains miniroot unix kernels for each of the client hardware platforms (unix.IP22, unix.IP32, etc). The ssssaaaa file contains the miniroot filesystem image which will be loaded onto each client's swap partition. See _p_r_o_m(1M) for more information on specifying a bootfile for a network boot. For example, if the command to boot the host from the prom is specified as bbbbooooooootttt ----ffff bbbboooooooottttpppp(((())))sssseeeerrrrvvvveeeerrrr::::////ddddiiiirrrr////ssssaaaa((((ssssaaaasssshhhhAAAARRRRCCCCSSSS)))) then the -b argument would be sssseeeerrrrvvvveeeerrrr::::////ddddiiiirrrr. If desired, the boot directory may also contain _i_n_s_t(1M) format software packages. The -b option is required unless -L is specified. The following commands can be used to make the directory /usr/local/boot a valid roboinst boot directory, assuming the IRIX Installation Tools CD is currently inserted and mounted under /CDROM: mmmmkkkkddddiiiirrrr ----pppp ////uuuussssrrrr////llllooooccccaaaallll////bbbbooooooootttt ccccpppp ////CCCCDDDDRRRROOOOMMMM////ddddiiiisssstttt////ssssaaaa ////uuuussssrrrr////llllooooccccaaaallll////bbbbooooooootttt ccccpppp ----rrrr ////CCCCDDDDRRRROOOOMMMM////ddddiiiisssstttt////mmmmiiiinnnniiiirrrrooooooootttt ////uuuussssrrrr////llllooooccccaaaallll////bbbbooooooootttt Note: the directory /usr/local/boot is tftp-accessible by default on SGI systems. However, if the boot directory you choose is not configured for _t_f_t_p(1C) access, the client will fail to boot the miniroot, and an error message such as "invalid argument" or "not a valid file to boot" may appear on the console. If this happens it may be necessary to edit the /etc/inetd.conf file on the boot server, and restart _i_n_e_t_d(1M). If the boot server and client are located on different networks, roboinst will require that bootp forwarding be enabled on routers between the client and the server. See the _b_o_o_t_p(1M) manual page, and also the online book _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g. PPPPaaaaggggeeee 2222 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) ----cccc _c_o_n_f_i_g_d_i_r Specifies an _r_o_b_o_i_n_s_t configuration server and directory, where the _r_o_b_o_i_n_s_t configuration files and scripts are located. The specified _c_o_n_f_i_g_d_i_r must contain an mmmmrrrrccccoooonnnnffffiiiigggg file, specifying automatic installation options (see _r_o_b_o_i_n_s_t__c_o_n_f_i_g(1M) for more information). If no _c_o_n_f_i_g_d_i_r is specified, it is assumed to be llllooooccccaaaallllhhhhoooosssstttt::::////uuuussssrrrr////llllooooccccaaaallll////bbbbooooooootttt////rrrroooobbbbooooiiiinnnnsssstttt////ccccuuuussssttttoooommmm. ----PPPP _d_i_s_k_p_a_r_t_i_t_i_o_n Specify a disk or partition other than the current root partition for automatic installation. You can either specify the SCSI id of the desired disk (a number between 1 and 15) or you can specify the full value for OOOOSSSSLLLLooooaaaaddddPPPPaaaarrrrttttiiiittttiiiioooonnnn. SSSSyyyysssstttteeeemmmmPPPPaaaarrrrttttiiiittttiiiioooonnnn will be set accordingly. See _p_r_o_m(1M) for more information on specifying values for OOOOSSSSLLLLooooaaaaddddPPPPaaaarrrrttttiiiittttiiiioooonnnn and SSSSyyyysssstttteeeemmmmPPPPaaaarrrrttttiiiittttiiiioooonnnn. NNNNooootttteeee:::: In order for the rrrroooobbbbooooiiiinnnnsssstttt ----PPPP _n command to successfully boot the miniroot, a copy of ssssaaaasssshhhh (from the IRIX 6.5 or later release) must be installed into the volume header of the target disk. Once ssssaaaasssshhhh has been installed, subsequent partitionings and installations will not remove it, though it may possibly get downgraded. When _r_o_b_o_i_n_s_t._s_w._c_l_i_e_n_t is installed, it puts a new copy of ssssaaaasssshhhh into the volume header of the system disk if the system is running a version of IRIX earlier than 6.5. The following commands (run as superuser) will copy that ssssaaaasssshhhh from the default system disk into the volume header on target disk _n: ddddvvvvhhhhttttoooooooollll ----vvvv ggggeeeetttt ssssaaaasssshhhh ////ttttmmmmpppp////ssssaaaasssshhhh ddddvvvvhhhhttttoooooooollll ----vvvv ccccrrrreeeeaaaatttt ////ttttmmmmpppp////ssssaaaasssshhhh ssssaaaasssshhhh ////ddddeeeevvvv////rrrrddddsssskkkk////ddddkkkkssss0000dddd_nvvvvhhhh rrrrmmmm ////ttttmmmmpppp////ssssaaaasssshhhh See _d_k_s(7) for a complete discussion of disk device names. ----ffff _d_i_s_t_r_i_b_u_t_i_o_n Specifies an _i_n_s_t(1M) _d_i_s_t_r_i_b_u_t_i_o_n which contains the _r_o_b_o_i_n_s_t(1M) client software. If _r_o_b_o_i_n_s_t__s_t_a_r_t does not exist on the specified host(s), _i_n_s_t(1M) is invoked to install the _r_o_b_o_i_n_s_t software from the specified _d_i_s_t_r_i_b_u_t_i_o_n (inst -f). ----FFFF _s_e_l_e_c_t_i_o_n_s_f_i_l_e Specifies an _i_n_s_t(1M) _s_e_l_e_c_t_i_o_n_s_f_i_l_e which specifies the location of the _r_o_b_o_i_n_s_t(1M) client software (see _i_n_s_t(1M) for more information on selections files). If _r_o_b_o_i_n_s_t__s_t_a_r_t does not exist on the specified host(s), _i_n_s_t(1M) is invoked to install the _r_o_b_o_i_n_s_t software using the specified _s_e_l_e_c_t_i_o_n_s_f_i_l_e (inst -F). ----LLLL Run _r_o_b_o_i_n_s_t in live mode. Do not bring the machine down to the miniroot in order to perform the automatic installation process. It is not possible to automatically reformat disks or change any networking parameters in live mode (only the "preinst", "inst", and PPPPaaaaggggeeee 3333 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) "postinst" keywords in the _m_r_c_o_n_f_i_g file are processed). Note that any output from a job running in live mode is normally suppressed, unless the ----mmmm option is used. ----nnnn Run _r_o_b_o_i_n_s_t in test mode. Verify the servers but do not actually start the automatic installation process. ----yyyy If no time is specified, force the automatic installation to start now. ----tttt _t_i_m_e Specifies a time at which the host should be restarted in automatic installation mode. The ttttiiiimmmmeeee is specified as for _a_t(1). If a time consisting of more than one word is specified, for example, 0000888811115555aaaammmm JJJJaaaannnn 22224444, then that time must be quoted ''''0000888811115555aaaammmm JJJJaaaannnn 22224444''''. If a time is specified, an _a_t(1) job will be submitted, and the host will be restarted at that time. It follows that the _a_t(1) queue must be enabled on the host. Cannot be used with ----nnnn. ----gggg _g_r_a_c_e-_p_e_r_i_o_d Specifies a grace period in seconds to be passed to the _s_h_u_t_d_o_w_n(1M) command on the client machine. The grace period allows active users some time to save their current work before the machine is shutdown and booted to the miniroot environment. The default grace period is 60 seconds. This option is ignored when -L is specified. ----NNNN _n_e_t_i_n_f_o_m_o_d_e Specifies how the miniroot gets the parameters necessary to connect to the network. Valid values are _D_H_C_P, _B_O_O_T_P_1_5_3_3, _L_O_C_A_L and its alias _N_O_N_E (case insensitive). LLLLOOOOCCCCAAAALLLL uses only the information available in the PROM variables and on the root filesystem, and is really only appropriate for upgrades. The others broadcast a BOOTP packet requesting network configuration from network servers, and DDDDHHHHCCCCPPPP also requests an IP address lease. If configured on the server (see _d_h_c_p__b_o_o_t_p for details), roboinst will set netmask, static routes, and a default route in the miniroot. The default if not specified is determined by the miniroot, and is the equivalent of specifying BBBBOOOOOOOOTTTTPPPP1111555533333333 in this release. This option is ignored when -L is specified. ----rrrr Remove an automatic installation job from the queue for the specified host(s). You cannot cancel an automatic installation in progress. ----llll List status of any automatic installation job for the specified host(s). This command only works if run on the host specified as the lllloooogggghhhhoooosssstttt for the specified host(s). See _r_o_b_o_i_n_s_t__c_o_n_f_i_g(1M) for more information about lllloooogggghhhhoooosssstttt. ----qqqq List the host(s) for which automatic installation jobs have been submitted. PPPPaaaaggggeeee 4444 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) ----mmmm _m_a_i_l_b_o_x Send the standard output and standard error of the _a_t(1) job to the specified email address. This option is only useful when the job is scheduled to run at a later time (see ----tttt). Without this option, all at-job output is suppressed. This option has no affect on messages generated during the miniroot portion of the job, nor on messages sent to the lllloooogggghhhhoooosssstttt (see _r_o_b_o_i_n_s_t__c_o_n_f_i_g(1M)). ----ssss _s_h_e_l_l Use the specified _s_h_e_l_l program to log into and execute commands on each client host. The default remote shell is ////uuuussssrrrr////bbbbssssdddd////rrrrsssshhhh((((1111CCCC)))). IIIINNNNIIIITTTTIIIIAAAATTTTIIIINNNNGGGG RRRROOOOBBBBOOOOIIIINNNNSSSSTTTT FFFFRRRROOOOMMMM TTTTHHHHEEEE PPPPRRRROOOOMMMM If the client is not up and running in multi-user mode, or is not accepting remote logins, a roboinst job can be initiated directly from the client's PROM command monitor. To enter the PROM, shutdown the system, and choose EEEEnnnntttteeeerrrr CCCCoooommmmmmmmaaaannnndddd MMMMoooonnnniiiittttoooorrrr from the system maintenance menu. (See the _p_r_o_m(1M) manual page for complete instructions.) Assuming the boot directory (see -b above) is located at server:/dir and the configuration directory (see -c above) is located at server:/config, then _o_n_e of the following commands will initiate a roboinst job from the PROM command monitor: boot -f bootp()server:/dist/sa(sashARCS) mrmode=custom mrconfig=server:/config boot -f bootp()server:/dist/sa(sash64) mrmode=custom mrconfig=server:/config The choice of sashARCS (32-bit sash) or sash64 (64-bit sash) will depend on the hardware type of the client system. For example, on Indy and O2 systems, sashARCS is used. On Octane and Origin platforms, sash64 is used. If the boot server (-b) is different than the config server (-c), then the latter should be specified in full IP-address notation, for example: boot -f bootp()server:/dist/sa(sash64) mrmode=custom mrconfig=92.26.80.118:/config The functionality of the ----NNNN option is implemented by prepending a special character to the configuration directory string. Each mode is specified by a unique character: !!!! (exclamation) for LOCAL, %%%% (percent sign) for BOOTP1533, and ++++ (plus sign) for DHCP. Not specifying any character lets the miniroot use its default (as in the above example). For example, to specify the RoboInst 1.0 behavior where DHCP is always used: boot -f bootp()server:/dist/sa(sash64) mrmode=custom mrconfig=+92.26.80.118:/config If disk partitioning of the system disk is to be performed, then an additional ddddiiiisssskkkksssseeeettttuuuupppp====ttttrrrruuuueeee argument must be specified, for example: PPPPaaaaggggeeee 5555 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) boot -f bootp()server:/dist/sa(sash64) mrmode=custom mrconfig=server:/config disksetup=true As a rule of thumb, the ddddiiiisssskkkksssseeeettttuuuupppp====ttttrrrruuuueeee argument should be given whenever the ddddiiiisssskkkksssseeeettttuuuupppp keyword is specified in the mrconfig file (see _r_o_b_o_i_n_s_t__c_o_n_f_i_g(1M)). The PROM has a limit on command-line length, and here are some ways to work around this problem. 1. Set the mrconfig variable on a separate command line. Note that mrconfig and netmask are volatie - they are not saved across reboot: setenv mrconfig 130.62.41.34:/roboinst/upgrade setenv netmask 0xffffff00 boot -f bootp()server:/dir mrmode=custom Setting netmask is only necessary if the default of 0xffff0000 is not desired, and there is no BOOTP 1533 or DHCP server configured to provide the netmask (see -N above.) 2. Use bbbboooooooottttpppp(((()))) as a shorthand for bbbbooooooootttt ----ffff bbbboooooooottttpppp(((()))). 3. Boot from the default location by putting the the ssssaaaa file and mmmmiiiinnnniiiirrrrooooooootttt subdirectory in /usr/local/boot on the boot server. Extract the the ssssaaaasssshhhhAAAARRRRCCCCSSSS and ssssaaaasssshhhh66664444 files into the same directory, and create symlinks that are more easily remembered. Models with 32-bit kernels should link to sashARCS, and models with 64-bit kernels should link to sash64: cd /usr/local/boot mkboottape -x -f sa sashARCS sash64 ln -s sashARCS o2 ln -s sash64 octane Then the PROM boot command will reduce to one of: bootp()server:o2 mrmode=custom mrconfig=... bootp()server:octane mrmode=custom mrconfig=... 4. If you use the default location for your mrconfig file (the /usr/local/boot/roboinst/custom directory on the same server where the sa file is located) then you can omit the mrconfig=server:/dir argument entirely: bootp()server:o2 mrmode=custom Note: if you are performing disk partitioning, you will have to add the disksetup=true argument if the swap partition has not already been moved to the beginning of the disk (see above.) PPPPaaaaggggeeee 6666 rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt((((1111MMMM)))) EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS A set of roboinst examples can be obtained by installing the optional subsystem roboinst.sw.examples using _i_n_s_t(1M) or _S_o_f_t_w_a_r_e _M_a_n_a_g_e_r(1M). NNNNOOOOTTTTEEEESSSS _r_o_b_o_i_n_s_t requires a software license in order to operate. Please refer to the _r_o_b_o_i_n_s_t release notes for more information on how to obtain and install software licenses; the release notes are in the _r_o_b_o_i_n_s_t._m_a_n._r_e_l_n_o_t_e_s subsystem. _r_o_b_o_i_n_s_t__s_t_a_r_t and _r_o_b_o_i_n_s_t__c_h_e_c_k are called by _r_o_b_o_i_n_s_t to perform various parts of the automatic installation process, do not run either directly. _r_o_b_o_i_n_s_t__s_t_a_r_t will fail if there is no space in $_T_M_P_D_I_R (////ttttmmmmpppp) to create temporary configuration files. FFFFIIIILLLLEEEESSSS /var/adm/roboinst/_h_o_s_t File indicating queued status of _r_o_b_o_i_n_s_t for the specified host(s). /var/inst/.roboinst_status A checkpoint file which indicates the loghost and the current state of automatic installation. bootserver:/bootfile The file the host loads when restarting to automatic installation mode, usually the _s_a file that contains the miniroot. configserver:/usr/local/boot/roboinst The host and directory which contains the configuration files for automatic installations. ccccoooonnnnffffiiiiggggddddiiiirrrr/mrconfig The configuration file which specifies automatic installation options. /_u_s_r/_s_h_a_r_e/_s_r_c/_R_o_b_o_I_n_s_t/* RoboInst examples. SSSSEEEEEEEE AAAALLLLSSSSOOOO roboinst_config(1M), at(1), inst(1M), bootp(1M), dks(7M), dhcp_bootp(1M), inetd(1M), nvram(1M), rsh(1C), shutdown(1M), prom(1M), and the online book _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g. BBBBUUUUGGGGSSSS The new options (-N, -s and -m) are not recognized and the roboinst will fail if the client has an older version of rrrroooobbbbooooiiiinnnnsssstttt....sssswwww....cccclllliiiieeeennnntttt installed. However, _r_o_b_o_i_n_s_t attempts to detect this and, if given the ----ffff option, will attempt to install the most recent version on the client. PPPPaaaaggggeeee 7777